Methods to manage the display of data entities and relational database structures

ABSTRACT

Methods that present typically large amounts of entity information with a graphical display that efficiently maps the display of a large number of OLAP objects to related relational database tables thereby retaining contextual information about the data associated with the objects and tables. The efficient mapping is enabled by the use of areas that contain and include objects. The preferred embodiment of the present invention enhances analysis, by OLAP techniques, of the objects and the associated relational database information. An embodiment of the present invention further operates in a recursive manner by enabling the objects to include and contain additional objects.

CROSS-REFERENCE TO RELATED APPLICATION

In co-pending application Ser. No. 10/319,056, entitled “Systems,Methods, and Computer Program Products to Modify the Graphical Displayof Data Entities and Relational Database Structures,” filed on Dec. 12,2002, by Tomlyn, assigned to the assignee of the present invention, andincorporated herein in its entirety by this reference, there isdescribed a method of modifying the graphical display of OLAP entities.Although not limited thereto, the present invention employs such amethod in one of its preferred embodiments.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention is directed to the field of graphical displays ofdatabase information. It is more particularly directed to managing thegraphical display of a typically large number of data objects thatefficiently presents mapped information about the relationship betweenthe data objects that are stored in a relational database and that areused in on-line analytical processing.

2. Description of the Background Art

A computer-implemented database is a collection of data, organized inthe form of tables. A table typically consists of columns that representdata of the same nature, and records that represent specific instancesof data associated with the table. A relational database is a databasethat is typically a set of tables containing information that ismanipulated in accordance with the relational model associated with thedata. The product marketed under the trademarks IBM DB2 stores the dataassociated with the database in tables, and each table has a name.

On-Line Analytical Processing (OLAP) is a computing technique forsummarizing, consolidating, viewing, analyzing, applying formulae to,and synthesizing data according to multiple dimensions. OLAP softwareenables users, such as analysts, managers, and executives, to gaininsight into performance of an enterprise, such as a corporation,through rapid access to a wide variety of data dimensions that areorganized to reflect the multidimensional nature of enterprise data,typically by means of hypotheses about possible trends in the data. Moreparticularly, OLAP techniques may be used to analyze data from differentviewpoints by identifying interesting associations in the information ina database. Therefore, OLAP is a decision support technique used in datamanagement for the purpose of modeling and analyzing businessinformation.

Data mining operations typically employ computer-based techniques toenable users to query structured data stored in computers in forms suchas: multidimensional databases, conventional databases, or flat computerfiles. More particularly, data mining involves extracting computer-basedinformation and enables a user to discover trends about thecomputer-based information.

An increasingly popular data model for OLAP applications, such as datamining, is the multidimensional database (MDDB). Often, data analystsuse MDDBs during interactive exploration of business data for findingregions of anomalies in the data. Before this data can be explored,modeling needs to be enabled for the business. Modeling a business foran OLAP application may require large amounts of metadata including dataentities.

In the past graphics tools have used objects, such as rectangledisplays, to represent data entities, such as relational databasetables. The objects are displayed so that they present the relationshipsbetween the data contained in the relational database tables. There hasbeen a problem representing the OLAP systems associated with the datawhile simultaneously representing the relational database datastructures associated with the storage of the data. For instance, datathat is stored in a relational database is typically stored in the formof two-dimensional tables. While, OLAP data representation typicallyincludes dimensional and measure data representation, relationaldatabase information is represented in the two-dimensional table format.Presentations in the past have attempted to show the mapping between therelational tables used to store the data and the OLAP objects that arepresented for OLAP data analysis.

Representing the mapping of OLAP data to relational database data isdifficult. Often, OLAP dimensional data objects are comprised of aplurality of relational database tables, and the plurality of relationaldatabase tables may include some of the same tables. By means of exampleOLAP data may include the number of sales that is measure data and alsodimensional data about the type of products that were sold, the timeframe of the sales, and the geographical market for the sales. In thepast, representation of such data might include multiple references torelational database tables that are used to represent a dimension or ameasure.

Given the large amount of OLAP data associated with the plurality oftables in databases, such as multidimensional databases and relationaldatabases, the related graphical representation may require a typicallylarge number of objects. Therefore, there may be many confusingrepresentations of OLAP dimensions and measures when the mappedrelational database table references are replicated to represent alltheir associations to OLAP dimensions and measures. This requires thedata analyst to understand the complicated mapping structure in order toreview information about the OLAP objects within the graphical displayduring analysis of OLAP data.

It would therefore be useful to be able to analyze typically largeamounts of entity information with a graphical display that efficientlypresents the mapping between the OLAP objects and the related relationaldatabase tables. When employing OLAP processing techniques it would beuseful to be able to efficiently analyze multidimensional data with agraphical display that minimizes the disadvantages associated withcurrent graphical displays. Graphical presentations in the past have notadequately displayed the mapping between the relational tables used tostore the data and the OLAP objects that are presented for OLAP dataanalysis.

From the foregoing it will be apparent that there is still a need toimprove the graphical display of a typically large number of objects sothat the mapping between OLAP objects and related relational databasetables is efficiently presented in order to enhance analysis of theobjects and the associated data.

SUMMARY OF THE INVENTION

An embodiment of the present invention relates to systems, methods, andcomputer products that efficiently manage and present entity informationin a graphical display. The graphical display efficiently maps OLAPobjects that represent entity information to related relational databasetables. An embodiment of the present invention enhances analysis of theobjects and the associated database data by techniques such as datamining of relational database information and OLAP data. Techniques ofthe past have not been able to sufficiently retain contextualinformation about the data and thereby improve the graphical display ofa typically large number of objects that are used with data analysistechniques such as data mining of relational database information,multidimensional data, and OLAP data.

The preferred embodiment of the present invention employs a techniquethat introduces areas that are containers for OLAP objects in thegraphical display. These areas that represent OLAP objects contain otherareas that represent database tables that are associated with the OLAPobject. The preferred embodiment of the present invention advantageouslykeeps information about relational database tables together so that,within a given area container, the associated relational database tablesare efficiently displayed. As discussed with reference to U.S. patentapplication, information represented in an area may be manipulated bytechniques such as expansion, reduction, and movement, to enhance OLAPdata analysis techniques.

The preferred embodiment of the present invention may rely on a typicalstar schema layout of data entities that includes a facts object,typically containing a single facts table, in the center of thegraphical display surrounded by dimension objects. A star schema is aset of relational tables including multiple main tables, sometimesreferred to as fact tables, and related dimension tables wherein thedimension tables intersect the main tables via common columns andwherein the dimension tables are each associated with a column in themain tables corresponding to each of the rows in the dimension tables.Because a star schema is simple, having few tables, it minimizes thecomplexity required to process database operations. This helps both toincrease performance speed and to ensure correct results of databaseoperations. Therefore many relational databases have been built in astar schema configuration to minimize database management overhead.

More particularly the star schema comprises fact tables, which arejoined to one or more dimension tables according to specified relationalor conditional operations. The fact tables hold measurement data, whilethe dimension tables hold attribute data. The dimension tables areusually joined to the fact tables with an equivalence condition.

The preferred embodiment of the present invention takes advantage of thestar schema configuration to manage graphical display of the OLAPentities and the database structures. Since the star schemaconfiguration may be logically represented by areas that represent facttables or dimensions, the preferred embodiment of the present inventionrecognizes the affinity between associated objects in the area andrepresents the associated objects in the graphical display. That is, theaffinity of OLAP objects in the same area is recognized and exploited byan embodiment of the present invention that groups the databasestructures associated with the OLAP objects in the same area.

An embodiment of the present invention is achieved by systems, methods,and computer products that improve the graphical display of a typicallylarge number of objects that may be used with data analysis techniquessuch as data mining of relational database information, multidimensionaldata, and OLAP data. A method comprises: (a) identifying the entities ina collection of data, (b) mapping the entities to objects that arerepresented in the graphical display, (c) identifying the objects in atleast one area, and (d) associating the objects within each at least onearea. It will be appreciated that the present invention may be embodiedin a graphical display that represents greater than two dimensions, suchas a three-dimensional graphical display. Also, an embodiment of thepresent invention further operates in a recursive manner by enabling theobjects to include and contain additional objects and areas.

An embodiment of the present invention novelly divides the graphicalpresentation into areas and allows objects to be manipulatedindependently within each area. More particularly, an embodiment of thepresent invention efficiently presents typically large amounts of entityinformation with a graphical display that efficiently maps the displayof OLAP objects to associated relational database tables therebyenhancing analysis of the objects and the associated relational databasedata by OLAP techniques. This provides added flexibility when attemptingto present many objects concurrently. It will be appreciated that theoperation of the present invention is not limited to a relationaldatabase, a multidimensional database, or OLAP applications but may beapplied to any computer-based graphical presentation that includes OLAPobjects. Other aspects and advantages of the present invention willbecome apparent from the following detailed description, taken inconjunction with the accompanying drawings, illustrating by way ofexample the principles of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 includes FIG. 1A and FIG. 1B;

FIG. 1A is a block diagram that illustrates the computer systems thatmay implement the present invention;

FIG. 1B is a block diagram that illustrates areas;

FIG. 2 is a block diagram that illustrates the problem addressed by thepresent invention;

FIG. 3 is a block diagram that illustrates an embodiment of the presentinvention;

FIG. 4 is a flow diagram that illustrates the present invention; and

FIG. 5 is a block diagram of a computer system suitably configured foremployment of the present invention.

In the following detailed description and in the several figures of thedrawings, like elements are identified with like reference numerals.

DETAILED DESCRIPTION OF THE INVENTION

As shown in the drawings and for purposes of illustration, theembodiment of the invention efficiently presents typically large amountsof entity information with a graphical display that efficiently mapsobjects to related relational database tables. An embodiment of thepresent invention enhances analysis of the objects and the associateddatabase data by techniques such as data mining of relational databaseinformation and is OLAP data. Existing systems have not been able tosufficiently improve the graphical display of a typically large numberof objects that may be used with data analysis techniques.

The present invention may be implemented with a graphical display thatincludes at least one area that includes objects that represent dataentities. The present invention enables users to analyze datarepresented as objects in a graphical display by representing associatedOLAP objects in the area. OLAP objects may also include and containother objects, thereby representing the OLAP objects in a recursiveconfiguration. The preferred embodiment of the present inventionadvantageously keeps information about relational database tablestogether so that, within a given area container, the associatedrelational database tables are efficiently displayed. This providesadded flexibility when attempting to present OLAP objects concurrently.

FIG. 1 includes FIG. 1A and FIG. 1B. FIG. 1A is a block diagram thatillustrates the computer systems that may operate with the presentinvention. As shown in FIG. 1 and in element 100, the preferredembodiment of the present invention may operate in a networked computersystem configuration. Therefore, a client computer system 102 maycommunicate with a server computer system 104 during the operation ofthe present invention. The object manager module 120 operates in theclient 102 or the server 104 to perform the preferred embodiment of thepresent invention. For example, information may be communicated toeither the server 104 or the client 102 via the user interface 117; andmay subsequently be used by the object manager module 120 to display alarge number of objects 126 in an area 124 and the objects 126 aremapped to relational database tables 11. The user interface 117 maycommunicate with the preferred embodiment of the present invention,either via batch input 119 or user input 118. Further, the database 110may be configured in the memory 558 of the client 102 or the server 104.Alternatively the database 110 may be configured in computer storagesuch as that of a disk 122. Element 558 is described with reference toFIG. 5.

According to the preferred embodiment of the present invention theobject manager module 120 operates by generating a graphical display 128that presents typically large amounts of entity information 130 byefficiently displaying OLAP objects 126 that represent the entityinformation 130, and the OLAP objects 126 are mapped to the relatedrelational database tables 111 in at least one area 124. Data entities130 may represent associations among objects 126; and about which data134 may be stored in a database 110, such as a multidimensional database132. Therefore by the operation of the present invention users maymanipulate and analyze a large number of objects 126 and see at a glancethe relationship between the objects 126 and the relational databasetable 111 that stores the associated data entity 130.

FIG. 1B is a block diagram that illustrates the facts objects 144 andthe dimension objects 148 that may be contained in at least one area124. Facts objects 144, Such as the one illustrated in FIG. 1B, mayinclude facts tables 143 that typically include measurement data 145.Dimension objects 148, such as the one illustrated in FIG. 1B, mayinclude dimension tables 149 that typically include attribute data 151.Therefore, by means of example the dimensions objects 148 may beassociated with a plurality of relational database tables 111.Relational database 110 operations, such as “join,” may be performed ondatabase tables 111, such as facts tables 143 and dimension tables 149.The fact tables 143 hold measurement data 145 that is typicallynumerical data 134. The dimension tables 149 hold attribute data 151that may be represented in either numerical or character format. In thepreferred embodiment of the present invention, an area 124 is novellyused to identify an affinity between associated objects 126 in the area124. In a star schema configuration 302 the attribute data 151, such asspecific information about product markets or product identificationdescriptors that is represented in a row in the dimension table 149 isused to identify columns in a facts table 143. Therefore, the preferredembodiment of the present invention novelly uses the star schemaconfiguration 302 to group associated objects 126 that are mapped torelated database tables 111. Elements 110, 111, and 134 are describedwith reference to FIG. 1, and element 302 is described with reference toFIG. 3.

As shown in FIG. 2, in the past it has been difficult to show ongraphical displays 128 the mapping between the relational tables 111used to store the data 134 and the OLAP objects 126 that are presentedfor OLAP data analysis. By further means of example, an object 126 mayrepresent a data entity 130 such as a facts table 143 or a dimensiontable 149 in a relational database 110. An object 126 may alternativelyrepresent OLAP data 134. In graphical displays 128 of the past theobjects 126 were represented by either the names of relational tables111 or by the names of dimension objects 148. Typically, when an OLAPobject 126 is minimized the dimension object 148 name is displayed. Whenthe OLAP object 126 is maximized in the graphical display 128 the namesof the dimension objects 148 and the relational tables 111 aredisplayed. Therefore, in the past the conceptual representation of OLAPobjects 126 was constrained to representations of relational database110 structures. The problems caused by manipulation of objects 126during analysis of the data entities 130 in the graphical display 128include obscuring some of the objects 126 and loosing the contextualreference of the objects 126, thereby reducing the information availableon the graphical display 128 for data analysis. Such problems areexacerbated by the ambiguity associated with the labels of the OLAPobjects 126 when the representations of the OLAP objects 126 areminimized. Elements 110, 111, 126, 130, and 134, and 143, 148, and 149are described with reference to FIG. 1.

In the present example, the following objects 126 are represented:Product_Dimension Object 216, Scenario_Dimension Object 218, Sales_FactObject 217, Supplier_Dimension Object 219, Market_Dimension Object 212,Time Dimension Object 215, and Accounts_Dimension Object 213. TheMarket_Dimension Object 212 is associated with and representsdimensional tables 149, such as the Market Details Table 221 and theMarket Table 223. By means of further explanation, the Market Table 223includes the following columns: PopulationID 232, RegionID 234, State236, and StateID 238. Also, the Market Details Table 221 includes thefollowing columns: Director 242, Region 244, and RegionID 246.

The problem in the past with the minimized representation of OLAPobjects 126, such as dimension objects 148, is that the same label forthe dimension objects 148 has been used to represent and identify thedimensional object 148 that is associated with different relationaldatabase tables 11, such as dimension tables 149. This is ambiguous andleads to confusion during data analysis. In the present example thelabel, Market_Dimension Object 212 is used to represent an associationwith at least the two dimension tables 149: Market Detail Is Table 221and Market Table 223.

FIG. 3 is a block diagram that illustrates the preferred embodiment ofthe present invention. The preferred embodiment of the present inventionemploys a technique that maps relational database tables 111 to objects126 that represent entities 130 and maintains the mapping byrepresenting objects 126 as containers for other objects 126 or tables111. Also, the novel use of an area 124 that contains objects 126represents the association between the objects 126 and the relationaldatabase tables 111. Elements 111, 124, and 126 are described withreference to FIG. 1.

By means of example the facts object 144 is mapped to the facts table143 TBC.FACT_TABLE 310. A dimension object 148, such as the ProductDimension Object 216 may include specific dimension tables 149, such as:TBC.ATTRIBUTE_OUNCES Table 312, TBC.LOOKUP_PRODUCT Table 314, andTBC.ATTRIBUTE_PACKAGE Table 316. Other dimension objects 148 included inthe present example are Market_Dimension Object 212, Time_DimensionObject 215, and Scenario_Dimension Object 218. The dimension objects 148intersect the facts object 144 via common columns and one dimensiontable 149 is associated with a column in the fact table 143corresponding to each of the rows in the dimension tables 149. In thepresent example, TBC.FACT Table 310 is a specific instance of the facttable 143 and is joined to one or more dimension tables 149 according tospecified relational or conditional operations. For example, theTime_Dimension Object.TBC.LOOKUP_TIME Table 330 is joined to theTBC.FACT Table 310. Elements 143, 148, and 149 are described withreference to FIG. 1.

The preferred embodiment of the present invention takes advantage of thestar schema configuration 302 to manage objects 126 in a particular area124 within a graphical display 128. For example, the graphical display128 of the present example illustrates a star schema configuration 302.An area 124 may include the Market_Dimension Object 212 and theTime_Dimension Object 215. The affinity of objects 126 in the same area124 is recognized and exploited by an embodiment of the presentinvention that groups objects 126 into at least one area 124. Since thestar schema configuration 302 may be represented by a series of areas124, the preferred embodiment of the present invention illustratesaffinity between associated objects 126 within a star schemaconfiguration 302 and the associated database tables 111 by manipulatingthe graphical representation of objects 126 in areas 124.

Further, the preferred embodiment of the present invention novellyenables representation of areas 124 and objects 126 in a recursivemanner, in which objects 126 may include and contain additional objects126 or areas 124, as shown in element 332.

FIG. 4 is a flow diagram that illustrates the present invention thatimproves the graphical display 128 of a typically large number ofobjects 126 that may be used with data analysis techniques such as datamining of relational database 110 information, multidimensional databaseinformation, and OLAP data 134. Initially, as shown in element 402, theentities 130 in a collection of data 134 are identified. Then as shownin element 404 the entities 130 are novelly mapped to objects 126. Next,as shown in element 406 the objects 126 are represented in the graphicaldisplay 128. Also as shown in element 407, at least one object 126 isassociated with at least one relational database table 111. According toa preferred embodiment of the present invention and as shown in element408, the objects 126 are associated with at least one area 124 so thatmanipulation of an object 126 within the area 124 may be treated as oneunit thereby retaining contextual information about the objects 126 andenhancing analysis of the objects 126 and the associated relationaldatabase 110 information by OLAP techniques. Elements 110, 111, 124,126, 128, 130, and 134 are described with reference to FIG. 1.

FIG. 5 is a block diagram of a computer system 500, suitable foremployment of the present invention. System 500 may be implemented on ageneral-purpose microcomputer, such as one of the members of the IBMPersonal Computer family, or other conventional workstation or graphicscomputer devices. In its preferred embodiment, system 500 includes auser interface 505, a user input device 510, a display 515, a printer520, a processor 555, a read only memory (ROM) 550, a data storagedevice 122, such as a hard drive, a random access memory (RAM) 540, anda storage media interface 535, all of which are coupled to a bus 525 orother communication means for communicating information. Although system500 is represented herein as a standalone system, it is not limited tosuch, but instead can be part of a networked system. The computer system500 may be connected locally or remotely to fixed or removable datastorage devices 122 and data transmission devices 545. For example, theserver computer system 104 and the client computer system 102 also couldbe connected to other computer systems 500 via the data transmissiondevices 545. Elements 102 and 104 are described with reference to FIG.1.

The RAM 540, the data storage device 122 and the ROM 550, are memorycomponents 558 that store data and instructions for controlling theoperation of the processor 555, which may be configured as a singleprocessor or as a plurality of processors. The processor 555 executes aprogram 542 to perform the methods of the present invention, asdescribed herein.

While the program 542 is indicated as loaded into the RAM 540, it may beconfigured on a storage media 530 for subsequent loading into the datastorage device 122, the ROM 550, or the RAM 540 via an appropriatestorage media interface 535. Storage media 530 can be any conventionalstorage media such as a magnetic tape, an optical storage media, acompact disk, or a floppy disk. Alternatively, storage media 530 can bea random access memory 540, or other type of electronic storage, locatedon a remote storage system.

Generally, the computer programs and operating systems are all tangiblyembodied in a computer usable device or medium, such as the memory 558,the data storage device 122, or the data transmission devices 545,thereby making an article of manufacture, such as a computer programproduct, according to the invention. As such, the terms “computerprogram product” as used herein are intended to encompass a computerprogram accessible from any computer usable device or medium.

Moreover, the computer programs 542 and operating systems are comprisedof instructions which, when read and executed by the server computersystem 104 and the client computer system 102, cause the server computersystem 104 and the client computer system 102 to perform the stepsnecessary to implement and use the present invention. Under control ofthe operating system, the computer programs 542 may be loaded from thememory 558, the data storage device 122, or the data transmissiondevices 545 into the memories 558 of the server computer system 104 andthe client computer system 102 for use during actual operations.

User interface 505 is an input device, such as a keyboard or speechrecognition subsystem, for enabling a user to communicate informationand command selections to the processor 555. The user can observeinformation generated by the system 500 via the display 515 or theprinter 520. The user input device 510 is a device such as a mouse,track-ball, or joy stick that allows the user to manipulate a cursor onthe display 515 for communicating additional information and commandselections to the processor 555. Those skilled in the art will recognizemany modifications may be made to this configuration without departingfrom the scope of the present invention.

When operating in accordance with one embodiment of the presentinvention, the system efficiently presents typically large amounts ofentity 130 information with a graphical display 128 that maps OLAPobjects 126 to relational database tables 111 for fast and efficientpresentation of the typically large amount of data 134 and that enablesefficient analysis of the data 134. It will be appreciated that thepresent invention offers many advantages over prior art techniques.Elements 111, 126, 128, 130, and 134 are described with reference toFIG. 1.

The present invention is typically implemented using one or morecomputer programs, each of which executes under the control of anoperating system and causes the server computer system 104 and theclient computer system 102 to perform the desired functions as describedherein. Thus, using the present specification, the invention may beimplemented as a machine, process, method, system, or article ofmanufacture by using standard programming and engineering techniques toproduce software, firmware, hardware or any combination thereof.

It should be understood that various alternatives and modificationsmight be devised by those skilled in the art. However, these should notbe viewed as limitations upon the practice of these teachings, as thoseskilled in the art, when guided by the foregoing teachings, may deriveother suitable characteristics of a similar or different nature. Thepresent invention is intended to embrace all such alternatives,modifications and variances that fall within the scope of the appendedclaims

Trademarks

IBM and DB2 are trademarks of International Business MachinesCorporation in the United States, other countries, or both.

1. A computer-implemented method to retain contextual information aboutdata, said computer having a graphical display and at least one entitythat represents said data, said method comprising: mapping at least onefacts table in a relational database to at least one Online AnalyticalProcessing (OLAP) object, wherein the at least one OLAP object is afacts object that is presented for OLAP data analysis, and wherein saidfacts table includes measurement data; mapping at least one dimensiontable in said relational database to a dimension object, wherein said atleast one dimension table includes attribute data, and wherein saiddimension object is an OLAP object that is presented for OLAP dataanalysis; generating said graphical display, wherein said graphicaldisplay includes a series of three separate areas represented withrectangles and including a left rectangle that is adjacent to a middlerectangle that is adjacent to a right rectangle, wherein said separateareas represent a star schema configuration, wherein different portionsof the star schema configuration are displayed in different areas,wherein each of said separate areas is a container that contains one ormore OLAP objects each represented with separate rectangles and containsone or more additional tables that are associated with said one or moreOLAP objects and each represented with separate rectangles within arectangle containing an associated OLAP object, wherein any OLAP objectrepresented by a rectangle includes at least one of an additional OLAPobject or a table each represented with separate rectangles, and whereinsaid one or more OLAP objects are manipulated independently within eachof said separate areas while retaining contextual information about theOLAP objects and displaying related tables within an area; anddisplaying said facts object in a first rectangle and said at least oneassociated facts table each in a separate rectangle within said firstrectangle that includes said measurement data in said middle rectangle,said dimension object represented in a second rectangle and said atleast one associated dimension table each in separate rectangles in saidsecond rectangle, wherein said first dimension object is in one of saidleft rectangle or said right rectangle, and relationships between saidfacts table and said dimension table in said graphical display to retainsaid contextual information about said data, wherein said relationshipsare shown across said separate rectangles in said graphical display,wherein one or more lines cross said separate rectangles and connectsaid measurement data of said at least one associated facts table insaid middle rectangle and said attribute data of said at least oneassociated dimension table in said left rectangle or said rightrectangle.
 2. The method of claim 1, further comprising: including saidrelational database having at least one table in said computer; andassociating said at least one object with said at least one relationaldatabase table to retain said contextual information about said data andsaid associated at least one relational database table.
 3. The method ofclaim 1, further comprising including another said at least one area insaid at least one object.
 4. The method of claim 3, further comprisingincluding another said at least one object in said another at least onearea.
 5. The method of claim 1, further comprising said datarepresenting OLAP data.